Operator CoFPortStatus

Operator Library: Hardware Platform

The operator monitors the status of a CXP fiber channel. It displays the current channel configuration and provides read access to various statistics and error counters.

Available for Hardware Platform
imaFlex 2 Dual 100

Resources

The operator mirrors the FiberConnection parameter setting into the FPGA Device Resources dialog as read-only parameters. You can see the FPGA device resources, if you open the FPGA Device Resources dialog from the Analysis menu. The device resources are read-only:

FPGA Device Resources

Figure 414. FPGA Device Resources


The operator uses a single resource either of the type Port[0] CoF Status Lane, or of the type Port[1] CoF Status Lane with index 0 to 3.

Deactivated Module Parameters

In the module parameters, the operator shows only the relevant statistics counters based on the FiberConnection parameter and whether a CoFCamera operator is instantiated. The operator can dock to:

  • A master camera lane,

  • an extension lane, or

  • any unused fiber lane, provided the hosting QSFP28 connector is configured for the CoF protocol in the AppletProperties operator.

If no CoFCamera is assigned to the QSFP28 connector, the parameter view will display only the FiberConnection parameter.

In this mode, the operator can't monitor anything meaningful.

When a CoFCamera is used and the operator is docked to an extension lane, only parameters relevant to the extension lane are displayed. Parameters that apply to the master lane are hidden in this mode.

When CoFCamera is used and the operator is docking to the master lane, all parameters are visible.

I/O Properties

Property Value
Operator Type None (since there are neither Inputs nor Outputs)

Supported Link Format

None

Parameters

FiberConnection
Type Static Write parameter
Default port_0_lane_0
Range {port_0_lane_0, port_0_lane_1, port_0_lane_2, port_0_lane_3, port_1_lane_0, port_1_lane_1, port_1_lane_2, port_1_lane_3}

The parameter FiberConnection defines on which QSFP28 port the camera is connected and which lanes of that port the camera operator is monitoring.

The selected QSFP28 port can be used only if the FiberProtocol parameter in the AppletProperties operator for that port is set to the CoF and not to DataForwarding.

If the FiberProtocol is set to DataForwarding and the CoFCamera operator attempts to map to that fiber port, the Design Rule Check (DRC) will generate an error message. In this case, the FiberConnection parameter will be marked as conflicted (red), and hovering over it will display a quick-tip help message explaining the conflict.

Only one CoFPortStatus operator can use the same hardware QSFP28 port on the same lanes. Mappings between multiple operators must be unique across the entire design.

RxStreamPacketCount
Type Dynamic Read parameter
Default 0
Range [0 : 2147483647]

This parameter represents the number of received stream packets:

  • Bits [29:0] represent the actual packet count.

  • Bit [30] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxStreamIncompleteCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how many received stream packets are incorrectly formatted, for example, when the end-of-packet indicator is missing:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxPacketCrcErrorCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts occurrences of CRC errors in received packets:

  • Bits [11:0] represent the number of errors.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxStreamPacketCrcError
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether CRC errors occurred in the received stream packets.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxControlAckPacketCrcError
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether CRC errors occurred in the received control acknowledgement packets.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxEventPacketCrcError
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether CRC errors occurred in the received event packets.

[Note] Visibility

This parameter is only visible for the master lane.
RxLengthErrorCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts cases where the actual packet length differs from the length specified in the packet header:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxStreamPacketLengthError
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether length errors occurred in the received stream packets.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxEventPacketLengthError
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether length errors occurred in the received event packets.

[Note] Visibility

This parameter is only visible for the master lane.
RxBridgeError
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts cases where the receiver bridge module detects protocol violations in the incoming data stream:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxUnknownDataReceivedCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts instances where unknown packet data is received which is not part of the CXP standard.

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxErrorCorrectedCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts errors received in packet headers and trailers that were corrected:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxBridgeCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether any errors in the received bridge data were corrected.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxControlAckPacketCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether any errors were corrected in received stream acknowledge packets.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxStreamPacketCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether any errors were corrected in received stream packets.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxTriggerPacketCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether errors were corrected in received trigger packets

[Note] Visibility

This parameter is only visible for the master lane.
RxTriggerAckPacketCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether errors were corrected in received trigger acknowledge packets.

[Note] Visibility

This parameter is only visible for the master lane.
RxEventPacketCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether errors were corrected in received event packets.

[Note] Visibility

This parameter is only visible for the master lane.
RxHeartBeatPacketCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether errors were corrected in received heartbeat packets.

[Note] Visibility

This parameter is only visible for the master lane.
RxUncorrectableErrorCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts errors received in packet headers and trailers which could not be corrected:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxBridgeNotCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether there were errors in received bridge data which could not be corrected.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxControlAckPacketNotCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether there were errors in received control acknowledgement packets which could not be corrected.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxStreamPacketNotCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether there were errors in received stream packets which could not be corrected.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxTriggerPacketNotCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether there were errors in received trigger packets which could not be corrected.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxTriggerAckPacketNotCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether there were errors in received trigger acknowledgement packets which could not be corrected.

[Note] Visibility

This parameter is only visible for the master lane.
RxEventPacketNotCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether there were errors in received event packets which could not be corrected.

[Note] Visibility

This parameter is only visible for the master lane.
RxHeartBeatPacketNotCorrected
Type Dynamic Read parameter
Default NO
Range {NO, YES}

This parameter indicates whether there were errors in received heartbeat packets which could not be corrected.

[Note] Visibility

This parameter is only visible for the master lane.
RxControlAckLostCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how many control packets were sent without receiving an acknowledgment within the CXP-defined timeout (200 ms):

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxControlTagErrorCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how many acknowledgments for control packets were received with a tag that doesn't match the expected tag sent in the corresponding request control packet:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

RxControlAckIncompleteCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how many incorrectly formatted acknowledgement packets were received, for example with a missing end-of-packet indicator:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane and the extension lane.

TxTriggerOverRequestCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how many trigger requests were skipped, because the transmitter was still busy sending the previous trigger packet:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane.
RxTriggerAckLostCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how many trigger packets were sent without receiving an acknowledgment packet within the CXP-defined timeout of 480 nanoseconds:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane.
RxTriggerAckErrorCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts the amount of errors in a trigger acknowledgment packet detected by the receiver:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane.
RxTriggerOverRequestCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how many trigger packets were received for which no acknowledgment could be sent, because the acknowledgment for the previous trigger was still in progress:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane.
RxTriggerLostCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how many received trigger packet were lost due to defective or not correctable trigger content:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane.
RxEventTagErrorCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how many tag errors in received event packets occurred due to gaps in the tag:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane.
RxEventOverAckCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how often an event packet is received, but the corresponding acknowledgment can't be sent, because the transmitter is still sending a previous event acknowledgment:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane.
RxEventIncompleteCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how many incomplete event packets were received, for example event packets with a missing end-of-packet indicator:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane.
RxHeartBeatIncompleteCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

This parameter counts how many incomplete heartbeat packets were received, for example heartbeat packets with a missing end-of-packet indicator:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane.
RxHeartBeatMaxPeriodViolationCount
Type Dynamic Read parameter
Default 0
Range [0 : 8191]

In the CXP 2.0 standard, the heartbeat period is defined as maximum 100ms. This means that during this time at least one heartbeat packet needs to be sent by the camera. This parameter counts how often this condition is not met:

  • Bits [11:0] represent the number of violations.

  • Bit [12] indicates overflow.

[Note] Visibility

This parameter is only visible for the master lane.
  Prev     Level Up     Next  
Content Top Home